-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ban references to Anaconda #119
Conversation
|
No module patch files, nf-core lint didn't complain? even if without any warnings. These files are just static files and will not be used if we don't run in conda. If we run in docker or singularity, it will still pull the prebuilt images remotely, default packages still included. |
Not that I could see. Not on CI either: https://github.com/sanger-tol/blobtoolkit/actions/runs/11500443253/job/32010690182?pr=119#step:6:423
Absolutely, updating the |
Closing in favour of #124 |
@tkchafin: this is a draft PR to test stuff. Feel free to use it.
I've first removed all references to "defaults".
It's not clear if we should be making patches for all modules.
nf-core modules patch
does detect the difference and makes a patch (I've done it forsamtools/flagstat
) butnf-core lint
andnf-core lint --release
don't flag it up. I want to see what the CI says.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).